home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX Patches 1995 September
/
SGI IRIX Patches 1995 Sep.iso
/
5.3_patches
/
patchSG0000567
/
patchSG0000567.idb
/
var
/
inst
/
help1.z
/
help1
Wrap
Text File
|
1995-09-07
|
87KB
|
1,983 lines
@ admin
admin
"admin" is a command on the Inst Main Menu and a short name for the
Administrative Commands Menu.
Give the "admin" command when you want to switch to the Administrative
Commands Menu.
Alternatively, if you want to execute a command from the Administrative
Commands Menu while you are in the Inst Main Menu, you can give the
command "admin <command>". It executes <command> as if your current menu
were the Administrative Commands Menu, but leaves you in the Inst Main
Menu.
The Administrative Commands Menu provides a variety of functions that are
not needed for most installations. See "help <command>" for each of the
commands on the Administrative Commands Menu to learn more about them.
The following commands are available from the Administrative Commands
Menu, but are not listed: "quit" and "help".
@ recalculate
recalculate
"recalculate" is a command on the Administrative Commands Menu.
The "recalculate" command causes inst to do a disk space calculation.
This means that it identifies the current amount of free disk space and
calculates the impact of installing the selected subsystems.
This command is needed only when you remove files during an installation
without using "go", i.e. you escape to a shell and use the rm command. In
this case, inst needs to recalculate its idea of the free disk space in
order to give you accurate disk space usage information.
@ config
config
"config" is a command on the Administrative Commands Menu.
The "config" command causes inst to display the list of installed
configuration files on the system. Configuration files are very likely to
need modification because they contain information that is often machine-
specific or site-specific. Config files with an "m" in the first column
of output are config files which size or checksum is different from the
version orginally installed. "config changed" outputs any config files
with the same name that have a .O or .N appended. The .O version of the
configuration file is your earlier version. The no-suffix version
contains changes that are required for compatibility with the rest of the
newly installed software, that increase functionality, or that fix bugs.
You should use diff(1) or gdiff(1) to compare the two versions of the
files and transfer information that you recognize as machine or site-
specific from the .O version to the no-suffix version. The .N version of
the configuration file is the new version. It contains changes or new
features that can be added to the no-suffix version of the configuration
file at your option. You should use diff(1) or gdiff(1) to compare the
two versions of the files and add changes that appeared in the new
software from the .N version to the no-suffix version if you want them.
@ load
load
"load" is a command on the Administrative Commands Menu.
The "load" command is used to open a file that contains a custom selection
of software. Such files were previously created using the "save" command.
@ save
save
"save" is a command on the Administrative Commands Menu.
The "save" command saves the current custom selections of software in a
file that you can later open by choosing "load".
@ hardware
hardware
"hardware" is a command on the Administrative Commands Menu.
The "hardware" command outputs internal hardware variables.
@ files
files
"files" is a command on the Administrative Commands Menu.
The "files" command may be used to list the names of the files that make
up subsystems that are available for installation. Other file information
displayed includes pending requests for the file (i.e. install, remove,
or keep), the installation state, the subsystem name, disk space delta,
and type.
Knowing the files that make up a subsystem can be helpful in determining
what specific functions are provided by the subsystem, and may help in the
subsystem selection process.
*** Change from old inst ***
The new inst allows viewing files from the distribution or the target. If
the subsystem is on both the target and distribution, the default now is
to show files on the target and distribution. To see only files on the
distribution use the command "files D <sybsystem>" which will only view
files on the distribution.
@ from
from
"from" is a command on the Inst Main Menu.
Use the "from" command to specify the location (or "source") of the
software distribution you wish to install. The source may be a local
tape, a local or remote CD-ROM drive, or a local or remote distribution
directory.
When inst first comes up, it prints a message about the default location
of the software distribution. If this location is correct, then there is
no need to give the "from" command immediately.
You can check to see what the current distribution source is after product
descriptions have been read by giving the "set" command. The value of the
"set" preference called "dist" is the current distribution location.
Giving a "from" command causes these things to happen:
o A connection with the distribution source is established.
o The product descriptions are read from the source. inst displays the
list of product descriptions it reads.
o The current list of selections for installation and removal is
forgotten.
You can use the "from" command four ways to specify the software
distribution source you want to use:
from Use prompting mode
from <source> Specify the distribution source explicitly
from $dist Specify that you want to reuse the current distribution
source
from none Don't use any distribution. Useful for removals only.
When using "from" in prompt mode, a list of former installation sites is
displayed. Enter the number of the distribution to use. The "set"
preference "install_sites_size" controls the number of install sites in
the list.
When using <source> or $dist and a non-tape distribution source, you can
append "/<product>" if you want to install just a single product. When
just a single product is read from a distribution directory or CD-ROM,
disk space checking is done just for that product and is substantially
faster.
The syntax of <source> depends on the distribution source and the user ID
you want to use:
<path> Local tape, CD-ROM, or distribution directory
<server>:<path> Remote CD-ROM, or distribution directory with
user ID "guest"
<user>@<server>:<path> Remote CD-ROM, or distribution directory with
user ID <user>
<server> is the name of the remote workstation and <user> is a user ID
that has been configured for installation (see the IRIS Software
Installation Guide). The possible values for <path> are:
/CDROM/dist For a local CD-ROM
<CDdir>/dist For a remote CD-ROM mounted at <CDdir>
<distdir> For a local or remote distribution directory in the
directory <distdir>
<nrtapedevice> For a local, no-rewind, byte-swapped, fixed block size
tape device whose device name is <nrtapedevice>, e.g.
/dev/rmt/tps0d2nrs.
Some examples of the "from" command are:
from none Read no distribution, and set the view to
target
from server:/CDROM/dist Read from a CD mounted at /CDROM on a remote
workstation
from joe@server:/d/distdir Read all product descriptors from a remote
distribution directory as user "joe"
from server:/d/distdir/nfs Read a single product "nfs" from a remote
distribution directory
from $dist Reuse last distribution source
from $dist/nfs Reuse last distribution source, but read
only the "nfs" product from it
from /dev/rmt/tps0d2nrs Read from a local tape drive on SCSI
controller 0, unit 2.
*** Change from old inst ***
The shorthand distribution "tape" (e.g. "from tape") for referring to the
local tape drive is no longer supported. Please specify the device
explicitly by controller and unit number.
Tape drive types other than QIC and DAT have not been tested.
Remote tape is not supported.
If you get an error message about not being able to read the product
description, there may be a problem in accessing the distribution or the
copy of the distribution itself may be bad. See "help networkerror" and
"help readerror" for more information.
@ networkerror
networkerror
This "help" topic provides information about problems with network access.
Network access errors can occur for the following reasons:
o NIS or BIND hosts databases do not have correct IP address information
for your workstation or the remote workstation, the proper IP address
is not in non-volatile RAM (NVRAM) on your workstation, and/or the
proper IP addresses are not set in the local or remote /etc/hosts
files.
o There may be a problem in the network configuration.
o The network connection may be blocked or unavailable.
o There might have been a failure during opening a file or reading a
directory.
o There may be a problem on the remote workstation.
Information about diagnosing network access problems and setting up a
remote account for installation is available in the IRIS Software
Installation Guide.
Information about network configuration is available in the IRIX Network
Administration Guide.
@ space
space
"space" is a command on the Administrative Commands Menu.
The "space" command gives disk space summary information. If the "set"
preference "delayspacecheck" is "off", it is the same as the "list" and
"step" commands. If "delayspacecheck" is "on", then giving the "space"
command forces the disk space calculation to be performed and a disk space
summary appears.
@ spaceerror
spaceerror
This "help" topic provides information about disk space problems.
As the available software grows and the number of user files increases,
disk space becomes more and more limited. If you cannot install because
of disk space problems, you must do one or more of the following:
1. Reduce the demand for disk space by installing fewer and/or smaller
subsystems.
You can accomplish this by using commands on the Inst Main Menu to
change the installation requests on a per-subsystem basis, until the
required space is sufficiently reduced. See "install", "keep",
"remove", and "step" for more information on how to do this.
2. Increase the available disk space by removing unnecessary user files
from the disk.
You can use the "versions" command to assist in this process. The
"versions user" command lists the names of files that are not part of
the software installed on the system. Some of these files may be
files that you don't need; they can be deleted by using the "sh"
command to escape to a shell and using the IRIX rm command to remove
them.
When using miniroot installation, your filesystems are mounted as
"/root" and "/root/usr", which means the pathnames must have "/root"
prepended. For example, if your home directory is "/usr/people/fred",
it is mounted as "/root/usr/people/fred" while running in the
miniroot. You can use the "shroot" command instead of "sh" to invoke
a shell that enables you to use the normal pathnames.
Overall free space on the disk is typically updated when you return
from shell so a "recalculate" command is unnecessary when removing
user files.
Note that if you use "rm" to remove files from installed subsystems,
you should use the "recalculate" command after returning to inst to
request that disk space be recalculated to reflect the changes.
3. Remove unnecessary subsystems from the disk.
The product distributions usually consist of software (*.sw.*), online
man pages (*.man.*), and InSight viewable documentation (*.books.*).
If you are short on space you may find that certain software, man
pages, or documentation groupings are not needed. Use the "showprods"
command without arguments to list all subsystems installed on the
disk. Use the "remove" command followed by the "go" command to remove
unnecessary subsystems.
Keep in mind that only one filesystem may be involved. It is possible
that the overflow is only on the "root" filesystem, in which case removing
files from the "/usr" filesystem won't help.
The disk space totals already account for removal of old versions of
software that are being replaced, obsoleted, or overwritten by the new
software. Removing subsystems explicitly prior to installing new versions
does not help with disk space problems.
@ go
go
"go" is a command on the Inst Main Menu.
Once the "install", "remove", and "keep" requests are complete, the
installations and removals are initiated when you give the "go" command.
Before the actual installations and removals are done, pre-installation
checks are done to make sure that the selections are valid. If any of
these checks fail, the installation and/or removal operations aren't done.
See "help check" for a list of these pre-installation checks.
@ conflicts
conflicts
"conflicts" is a command on the Inst Main Menu.
It is used to view, or resolve, the current installation conflicts.
conflicts If no arguments are given, the current conflicts are
displayed. Each conflict is identified by a number.
Along with each conflict a set of choices is given
which will resolve that conflict. Each choice is
identified by a number/letter pair (1a, 2c, etc.)
conflicts choice .. If choices are given, inst resolves the conflicts by
applying the specified choices.
The easiest way to resolve conflicts is to issue the "conflicts" command
once to see the conflict list, then issue the command again, along with
your choices. Alternatively, you may continue using the "install",
"remove" or "keep" commands to modify the current installation request.
All installation conflicts (missing prerequisites, missing required
subsystems, incompatible subsystems, etc.) must be resolved before giving
the "go" command.
In the example below, a subsystem (insight.sw.client) is selected for
removal, but other subsystems list it as a prerequisite. In order to
resolve the conflict, either insight.sw.client must not removed, or the
other products must also be removed:
Inst> remove insight.sw.client
Inst> conflicts
insight.sw.client (IRIS InSight Viewer, 2.3) cannot be removed because
other products depend on them:
1a. Do not remove insight.sw.client (IRIS InSight Viewer, 2.3)
1b. Also remove
dev.books.IRIX_NetPG (IRIX Network Programming Guide)
dev.books.IRIX_SysPG (IRIX System Programming Guide)
WorkShop.books.WRKSHP_UG (WorkShop User's Guide)
Resolve conflicts by typing "conflicts choice choice ..."
Or try help conflicts
Inst> conflicts 1b
No conflicts
@ install
install
"install" is a command on the Inst Main Menu and a keyword argument for
the "install", "keep", "list", "remove", and "step" commands.
The "install" command is used to identify or select subsystems that should
be installed. Note that this is a request only; the installation does not
occur until you use the "go" command. Until then, you may alter your
selections as you wish, using the "install", "keep", and "remove"
commands, or "step" mode. See also "help selection".
You can see the subsystems available for installation with the "list"
command. Subsystems selected for installation have an "i" in the first
column.
inst makes an initial guess at the subsystems you are likely to want
installed which takes into account whether your workstation has "seen" the
product before.
*** Change from old inst ***
The new inst initial selections are based on the preference
"install_selection". The default value of this preference is "upgrade".
Only subsystems on the distribution which have an older version installed
are selected by default for installation.
The keyword "install" (or just "i") is a shorthand for all of the
subsystems that are selected for installation (i.e. have a "i" at the
beginning of the line in a "list" or "step" display).
@ keep
keep
"keep" is a command on the Inst Main Menu and a keyword argument for the
"install", "keep", "list", "remove", and "step" commands.
The "keep" command of the Inst Main Menu is used to identify or select
subsystems that should be kept as-is on the disk. It cancels any install
or remove requests you have made for the specified subsystems, so that the
existing version on the disk, if any, remains undisturbed. See also "help
selection".
*** Change from old inst ***
Because of the new "view" command. "k" is only displayed on subsystem on
the target.
The keyword "keep" (or just "k") is a shorthand for all of the subsystems
that are marked for no change (i.e. have a "k" at the beginning of the
line in a "list" or "step" display).
@ list
list
"list" is a command on the Inst Main Menu.
The "list" command shows the subsystems that make up the currently
available distribution or the subsystems that are currently installed on
the target. Each subsystem represents a collection of files that can be
installed or removed as a unit.
Any of the single letter column values explained below can be used as
keyword modifiers to the list command. See "help keywords" for more
information.
Included in the listing are several columns of information about each
subsystem. The first column is one of the following characters, which
indicate the current request for the subsystem:
i Install this subsystem after removing the old version, if any
r Remove the old version subsystem
k Keep this subsystem as-is on the disk
(blank) Do not install this subsystem
The second column indicates the current status of the subsystem.
The possible value for subsystems on the distribution are:
S This version already installed
U An older version of some related subsystem is installed
O A newer version of some related subsystem is installed
N A new subsytem with no related version installed
The possible value for subsystems on the target are:
I Subsytem is currently installed
R Subsystem was installed but removed
blank Subsytem was never installed
The next column shows the name of the product, image, or subsystem. These
names are used as arguments to "list", "install", "keep", "remove",
"step", and "versions". Following some of the names in "[]" are single
character codes:
d means that the subsystem has been designated a default subsystem
b means that the subsystem must be installed from the miniroot
r means that the subsystem has been designated a required subsystem
The last column gives a brief description of the subsystem.
*** Change from old inst ***
The size numbers are no longer space deltas. They represent the total size
of the subsystem.
The deltas about the installation and removal request and the overhead are
no longer displayed. The summary at the bottom of the list provides
information on how the sum of the installation and removal requests will
affect the amount of disk space on each filesystem:
Net change in blocks The total of the previous three values,
i.e. the total projected disk space change
for the requested operations
Blocks available The free space available on the filesystem
If "Net change in blocks" is larger than "Blocks available", the
installation cannot proceed because of the extreme likelihood of running
out of disk space. The problem is detected when you issue the "go"
command. Get help on "spaceerror" if you run into such disk space
problems.
@ selection request
selection request
"selection" and "request" are important terms in the installation process.
You make "selections" and "requests" with the "install", "keep", "remove",
and "step" commands, that is you tell inst that you want it to install,
not install/not remove (keep), or remove subsystems. Since these commands
do not take effect immediately, there is a concept of your current
selections or requests. Your current selections can always be viewed with
the "list" command. It shows the current selection status of each
subsystem in the first column of its output.
You can change the current letter (request) to a different letter
(request) using the "install", "remove" and "keep" commands, or by typing
a letter in "step" mode as shown below:
Current Desired Step
Request Request Command Key
i i <Enter> or n or i
i r remove r
i k keep k
i blank keep k
r i install i
r r <Enter> or n or r
r k keep k
r blank keep k
k i install i
k r remove r
k k <Enter> or n or k
k blank (k and blank have the same effect)
blank i install i
blank r remove r
blank k (blank and k have the same effect)
blank blank <Enter> or n or k
@ mkfs
mkfs
"mkfs" is a command on the Administrative Commands Menu. It can be used
during miniroot installations only.
If a brand new disk is being used, or if the current contents of the disk
or a filesystem on the disk are to be completely discarded, you can make
new filesystems with this command.
By default, with no arguments, new filesystems are made on the root "/"
and user "/usr" filesystems. Alternately, you can specify the disk device
to operate on by name. When specifying the disk device explicitly, use
the same block device name as appears in the output of the "admin mount"
command for the desired device.
If there are filesystems mounted below the filesystem to be mkfs'd, then
these other filesystems are automatically unmounted before the mkfs is
done, and remounted afterward.
The "mount" command on the Administrative Commands Menu shows what the
device names for the root and user filesystems are.
Note that all existing files, including all directories, programs, and
data, are lost when a new filesystem is made. Proceed with caution. You
are warned if there is already a filesystem on the named device, and
prompted for a confirmation before any new filesystem is made.
@ mount
mount
"mount" is a command on the Administrative Commands Menu.
To find out what is mounted, to change the default mountings, or to add
new mountings that are unknown to inst, use the "mount" command. Without
arguments, it displays what is currently mounted. The two arguments are
the block device name and the mount point. You can specify the mount
point in absolute terms, although it is mounted relative to /root for the
duration of the installation.
@ quit
quit
"quit" is a command on the Inst Main Menu. It is also available from the
Administrative Commands Menu.
Use "quit" to exit from the inst program.
If you have made installation and/or removal requests, but have not
performed the requests with the "go" command, you are asked to confirm
whether or not you really want to quit. If you type "yes", the requests
are discarded. If you type "no", you are returned to your current menu.
You can use the "list" command on the Inst Main Menu to find out what the
requests are, if you wish, and/or the "go" command to perform them.
If you are using the miniroot, you are asked if you are ready to restart.
If you answer "no", you return to the Inst Main Menu. If you answer
"yes", your system is rebooted and comes up running the new software. You
can answer "sh" to shell escape and "h" to receive help about the restart
options.
@ remove
remove
"remove" is a command on the Inst Main Menu, a keyword for the "install",
"keep", "list", and "step" commands.
Use the "remove" command to request that installed subsystems be removed
from the system. The removal does not occur until you enter the "go"
command. Until then, you may change the requested operations for any or
all subsystems. To undo a "remove" request, use the "keep" command. An
alternative to the "remove" command is the "step" command. It enables you
to decide interactively, subsystem by subsystem, which subsystems you want
to remove. See also "help selection".
inst automatically removes old versions of subsystems you have selected
for installation so it is not necessary to explicitly remove them.
Typically, you remove software when you no longer need it, or when your
disk is so full that you must remove something in order to install
something you need more.
The keyword "remove" (or just "r") is a shorthand for all of the
subsystems that are selected for removal (i.e. have a "r" at the beginning
of the line in a "list" or "step" display).
@ removed R
removed R
"removed" is a keyword argument for the "install", "keep", "list", and
"step" commands. For example, "list R" shows all subsystems that were
once installed on the target and later removed.
An "R" (removed) single letter code in the third column of "list" or
"step" output indicates that a this is a subsystem was once installed on
the target, and later removed.
@ set
set
"set" is a command on the Administrative Commands. It is also available
from the Inst Main Menu.
The "set" command is used to examine and change the settings of
preferences. If you provide no arguments, the current settings are
displayed. If you provide just the name of a preference, information
about the preference is displayed. If you provide the name and the new
value, the preference setting is changed. The "set" command is available
from the Inst Main Menu as well, even though it isn't listed.
*** Changes from old inst ***
Just providing the name of a preference no longer sets the preference to
its default value.
Some preference settings are saved in the installation history database
when you set the new value of the resource. The name of the file has
changed from ".options" to ".swmgrrc"
Help on a specific preference is no longer available by asking for "help"
on that preference. Use the command "set <preference>" for help on a
preference "<preference>".
@ sethostname
sethostname
"sethostname" is a command on the Administrative Commands Menu.
Used in the miniroot only to prompt the user for the network hostname of
the local workstation. Automatically restarts the networking using the
provided hostname.
@ sethostipaddr
sethostipaddr
"sethostipaddr" is a command on the Administrative Commands Menu.
Used in the miniroot only to prompt the user for the network ip address of
the local workstation. Automatically restarts the networking using the
provided ipaddr.
@ sh
sh
"sh" is a command on the Administrative Commands Menu. It is also
available from the Inst Main Menu.
The "sh" command invokes an IRIX shell, from which you have full access to
IRIX and the filesystems. If you provide arguments, they are taken as a
single IRIX command to be executed immediately.
When using the miniroot, remember that your filesystems have been mounted
relative to "/root", which means that they (temporarily) have different
pathnames; e.g. what is normally known as "/usr/people/guest" is mounted
as "/root/usr/people/guest". The "shroot" command is an alternative to
"sh" that enables you to use the familiar pathnames while you are working
in the shell. Also remember that a very limited set of IRIX commands is
available if you are using miniroot installation.
The program that is invoked is determined by the setting of the "shell"
option; if the value of that option is not a valid program, the command
fails. The default is based on the SHELL environment variable, and is
normally either "/bin/sh" or "/bin/csh".
@ shroot
shroot
"shroot" is a command on the Administrative Commands Menu. It is also
available from the Inst Main Menu.
The "shroot" command invokes a "chrooted" IRIX shell, from which you have
full access to IRIX and the filesystems. If you provide arguments, they
are taken as a single IRIX command to be executed immediately.
When using the miniroot, the filesystems are mounted relative to "/root",
so that "/usr/people/guest", for example, is mounted as
"/root/usr/people/guest". To reduce the confusion under such
circumstances, the "shroot" command uses the "chroot" system call to
invoke the shell as if "/root" were its root directory, i.e. "/root"
becomes "/" for all references. Thus files can be referred to with their
normal pathnames.
It is not possible to use "shroot" if certain key files are not present
under the installation root. The missing files are listed, and the shell
that is invoked is not chrooted; i.e. files must be referred to as
"/root/...".
The program that is invoked is determined by the setting of the "shell"
option; if the value of that option does not identify a valid program, the
command fails. The default is based on the SHELL environment variable,
and is normally either "/bin/sh" or "/bin/csh". The specified program
must exist in the filesystem under the installation root, not the current
root.
@ step
step
"step" is a command on the Inst Main Menu. In step mode, inst displays
each product (or image or subsystem, depending on your view), then waits
for you to press a single character command to mark that product for
installation, removal or no action (keep).
Your current view (see "help view") controls which products are displayed
by step. Optional arguments to the step command further control what
products are displayed, as described at the end of this help article.
Available step mode commands are:
i Mark this product for installation
r Mark this product for removal
k Keep; cancel any install or remove request
n, +, <Enter> Step to the next product
p, - Step back to the previous product
arrow keys up, down, left and right; same as p, n, k, i
u Upgrade; install corresponding product from distribution
d Default; mark for installation only if default product
I,R,K,N,P,U,D Automatically apply corresponding lower case command to
remaining subsystems in this product
/pat Find a product matching the given pattern
f List the files in this product
l Redisplay all previous products
q Quit step mode
The "step" command takes keyword arguments (see "help keywords") and
product, image, and subsystem name arguments.
Some example uses of such arguments are:
step installable Use step mode on all subsystems that can be installed
(this is the default)
step upgrade Use step mode on all subsystems marked `U'
step eoe2 Use step mode on all eoe2.*.* subsystems
@ umount unmount
umount unmount
"umount" is a command on the Administrative Commands Menu.
The "umount" command of the Administrative Commands Menu is used to
unmount disks that inst has mounted by default, or that have been mounted
with the "mount" command. The filesystem's name remains in inst's device
table even after the filesystem is unmounted.
Note that in some cases, filesystems mounted under the specified file
system have to be unmounted first.
@ incompatible
incompatible
Subsystems are designated incompatible when the system will not operate
correctly with the new version of one subsystem and an older version of
one or more other subsystems that are already installed.
*** Change from old inst ***
You will receive conflict messages when you issue the "go" command. These
imcompatible conflicts must be resolved before a "go" command can be
executed.
Incompatible subsystems or products may not be installed, unless the
conflicting subsystem is removed first. Some subsystems are designated
incompatible because they are older versions that prevent the system from
operating. These are usually designated as incompatible with the
eoe1.sw.unix subsystem. In general, you must obtain an appropriate
version of the subsystem if you wish to continue using it.
Additionally, entire products may be marked as compatible with only some
hardware configurations. This is normally true only with hardware
specific releases. Attempting to select any subsystem in such products
will result in a message that the subsystem was not selected because it is
not compatible with the machine. If you receive this message, please
consult your release notes for the supported hardware configurations.
Subsystem incompatibilities can be overridden using the
"override_conflices" option. Use this option with extreme care since
installing incompatible software can lead to erroneous system behavior.
See "help conflicts" for more on resolving imcompatible conflicts.
@ i
i
An "i" (install) single letter code is used in the following ways:
o When it appears in the first column of "list" and "step" output, it
indicates that the subsystem is currently selected for installation.
o In "step" mode, the "i" key is used to request installation for the
currently displayed subsystem.
o An "i" (or "install") can be used as an argument to the "list",
"step", "keep", and "remove" commands as a shorthand for the
subsystems currently selected for installation. For example, "list i"
lists subsystems currently selected for installation.
@ k
k
A "k" (keep) single letter code is used in the following ways:
o When "k" appears in the first column of "list" and "step" output, it
indicates that there is a related version of the subsystem on the
disk, but no installation or removal of that subsystem will occur when
you give the "go" command.
o In "step" mode, the "k" key is used to request no change for the
currently displayed subsystem.
o A "k" (or "keep") can be used as an argument to the "list", "step",
"install", and "remove" commands as a shorthand for the subsystems
currently selected as "keep". For example, "remove k" changes the
request for each subsystem marked "k" to "r".
@ r
r
A "r" (remove) single letter code is used in the following ways:
o When an "r" is in the first column of "list" and "step" output, it
indicates that the subsystem is currently selected for removal.
o In "step" mode, the "r" key is used to request removal for the
currently displayed subsystem.
o An "r" (or "remove") can be used as an argument to the "list", "step",
"install", and "keep" commands as a shorthand for subsystems currently
selected for removal. For example, "keep remove" changes the request
for each subsystem selected for removal to keep ("k").
o An "r" is displayed next to the names of subsystems that are required
for proper system operation.
@ *
*
A "*" is used as a wildcard in product, image, and subsystems names. See
"help wildcard".
@ wildcard
wildcard
Several shell-type wildcards can be used in product, image, and subsystem
names:
* Matches zero or more characters in the product, image, or
subsystem portion of a name
? Matches a single character
[<range>] Matches a range of characters, for example [a-z] matches any
of the characters a through z
These shell-type constructs apply only to the product, image, or subsystem
portion of the name they are used in. Thus, it applies from the previous
`.' (or beginning of the name) to the next `.' (or end of the name).
@ .N
.N
".N" (newer) is a suffix that is sometimes added to the names of
configuration files.
A file whose name ends in ".N" is a new version of a configuration file
that you have previously modified. The intent is to preserve your
existing configuration file, but make the new version available for your
perusal. You may wish to combine features of the existing and new
configuration files into a single version, or use the new file as-is, or
simply remove the new file and not use any of the new features it
provides. Once you have made the appropriate edits to the no-suffix
version of the configuration file, you can delete the ".N" version.
@ .O
.O
".O" (older) is a suffix that is sometimes added to the names of
configuration files.
A file whose name ends in ".O" is a configuration file from an older
release that you have modified. The new version of the file from the
release is considered important for proper system operation, and so has
been put into place. You may wish to merge in features from your saved
".O" version. Once you have made the appropriate edits to the no-suffix
version of the configuration file, you can delete the ".O" version.
@ keywords
keywords
"keywords" is an optional argument for the "install", "keep", "remove",
"list", and "step" commands.
Keyword arguments are shorthand ways of naming groups of subsystems. The
keywords are "all", "default", "install", "installable", "installed",
"keep", "newer", "older", "removable", "remove", and "uninstalled". The
"list" command takes three additional keywords: "images", "products", and
"sizes".
If more than one keyword is given, the meaning is the intersection of the
keywords. This means that the set of subsystems that is operated on is
that set of subsystems that satisfies all of the criteria for all of the
keywords used.
The following list gives each keyword, its abbreviation if it has one, and
a brief description. For more information, see "help <keyword>" for each
of the keywords.
all, a All subsystems in "showprods -a" output plus all
subsystems in the software distribution
default, d All subsystems in the distribution that are marked with
"d".
distribution All subsytems in the distribution
downgrade, D All subsystems that have a version installed that is
newer than the version in the software distribution
install, i All subsystems that are selected for installation
installable, A All subsystems in the software distribution
installed, I All subsystems that are installed on the target.
keep, k All installed subsystems that are in the software
distribution, but not selected for installation or
removal
miniroot, b All subsystems that must be installed in the miniroot or
require a reboot to complete installation.
new, N, n All subsystems that don't have a version installed or
even a version once installed and later removed.
notinstalled All subsystems that have a version on the target which
was not installed. The version on the target was either
removed or never installed.
patches All patches in the distribution.
patchupgrade, P All patches in the distribution that are upgrades to
installed patches.
removable, L All of the installed subsystems that can be selected for
removal
remove, r All of the subsystems that are selected for removal
removed, R All subsystems that were once installed.
required, q All of the subsystems that are required for proper
operation of the workstation
same, S, s All subsystem that have an identical version installed
target All subsytems on the target
uninstalled Subsystems that meet all of these conditions: they were
available for installation in the past, they are not
currently installed, they don't have a version in the
distribution, and they are not maint subsystems
upgrade, U All subsystems that have a version installed that is
older than the version in the software distribution
upgraded, u Any subsystem on the target that is being removed as part
of an installation of a related (typically newer) version
of the product from the distribution.
@ filter
filter
The filter command on the view submenu lets you see or hide products shown
by list and step, based on such attributes as whether they are upgrades,
downgrades, installed, removed, ...
Each filter attribute applies just to products on the distribution {dist},
or just to products on the target {targ}.
The "filter" command with just one argument turns that filter on.
When a filter is on, that means that products matching that attribute are
visible. When a filter is off, products matching that attribute are not
visible (unless they match some other filter that is on).
filter all [on|off] Show all products on distribution {dist}.
filter new [on|off] Show new, not installed, products {dist}.
filter upgrade [on|off] Show upgrades, newer versions of what is
installed {dist}.
filter same [on|off] Show products that are already installed, at
the same version {dist}.
filter downgrade [on|off] Show downgrades, older versions of what is
installed {dist}.
filter notinstalled [on|off] Show any products on distribution that
aren't upgrades, downgrades, new or same -
typically products you chose to not install
earlier {dist}.
filter installed [on|off] Show products currently installed {targ}.
filter removed [on|off] Show products installed, then removed {targ}.
filter rejected [on|off] Show products intentionally not installed in
an earlier inst session {targ}.
@ main
main
The Inst Main Menu is the first menu that is displayed to an inst user.
This menu provides all of the commands needed during a typical
installation session.
There are several other commands that are available from this menu, but
are not listed. They are "set", "sh", and "shroot".
@ product image subsystem
product image subsystem
This "help" topic give the definitions of product, image, and subsystem.
Each of these words describes a collection of files.
Products are the largest collections of files. Usually there is one
product for each software option you can purchase. Products have short
names, such as "ftn" for Fortran 77. "eoe1" and "eoe2" are the product
names for the software that is shipped with each workstation.
Products are typically divided into two (or sometimes more) images. Most
products have a "sw" image that contains software and a "man" image that
contains manual pages and online release notes. The name of an image is
formed by concatenating its product name, a `.', and the image type. For
example, "eoe1.sw" and "eoe1.man" are image names.
Images are subdivided into subsystems. Each subsystem is a group of
related files that enable particular functions. The groupings of files
into subsystems are chosen so that most customers will want all of the
files in a subsystem or none of them. Subsystem names are formed by
taking the image name and appending a `.' and a short name for the
function of the subsystem. Some examples are eoe1.sw.audio and
eoe2.man.imagetools.
@ args
args
"args" stands for the arguments to the "view" and "date" commands.
The arguments to the "date" inst commands are identical to the arguments
of the IRIX date(1) command. See the manual page for details. Some
examples of args are:
date 1022160791 Set the system date to 4:07 p.m. October 22, 1991. The
format is mmddhhmmyy.
See "help view" for information on args to the "view" command.
@ date
date
"date" is a command on the Administrative Commands Menu.
The "date" command can be used to check and set the system date. It is
very important during miniroot installations to have the date set
correctly because reconfiguration of the kernel can fail if there are
problems with the system date.
@ devices
devices
"devices" is the argument to the "mkfs" command. It is one or more
"special" names that are passed to the mkfs(1M) IRIX command. See
mkfs(1M) for the syntax of "special". If no "devices" argument is given
to "mkfs", the default is to make / and /usr filesystems after confirming
with a prompt that you want to destroy everything on your / and /usr
filesystems.
@ dir
dir
"dir" is an argument to the "mount" and "umount" commands. It is a
directory name with the same syntax as the dir argument of the mount(1M)
and umount(1M) commands.
@ fsname
fsname
"fsname" is an argument to the "mount" and "umount" commands. It is a
filesystem name with the same syntax as the fsname argument of the
mount(1M) and umount(1M) commands.
@ names
names
"names" is an argument to the "files", "list", "install", "keep",
"remove", and "step" commands. It is one or more product, image, or
subsystem names. These names can include the shell-type wildcard. See
"help wildcard" for more information.
@ preferences
preferences
The "set" command takes arguments that are called preferences. These
preferences have values that control the behavior of inst, control the
feedback provided by inst, and have miscellaneous other functions. Give
the command "set" to get a list of preferences.
@ options
options
See "help preferences".
@ source
source
"source" is the argument to the "from" command. It is the name of the
software distribution source you plan to use next. It can be a tape drive
on your workstation with a tape in it, a CD-ROM drive on your workstation
with a CD in it, a distribution directory on your workstation, a CD-ROM
drive on a remote workstation with a CD in it that has been mounted by
cdinstmgr, or a distribution directory on a remote workstation. See
"help from" for the syntax of source.
@ all a
all a
"all" is a keyword argument for the "install", "keep", "list", "remove",
and "step" commands.
The "all" (or "a") keyword is a shorthand for all of the subsystems inst
has ever seen (i.e. the list of subsystems you get with "showprods -a"
plus anything that it is seeing for the first time in the current
distribution) except for maint* subsystems from the past.
@ default d
default d
"default" is a keyword argument for the "install", "keep", "list",
"remove", and "step" commands. Default subsystems are recommended for
installation in the absence of more refined criteria, but need not be
installed or retained if not needed.
The "default" (or just "d") keyword is a shorthand for the subsystems that
have been chosen by the manufacturer as a basic or "starter" set of
subsystems. "Default" subsystems are marked with "d" after the subsystem
name in a "list" or "step" display.
*** Change from old inst ***
The old inst used the symbol "*" for default subsystems.
@ installable A
installable A
"installable" is a keyword argument for the "install", "keep", "list",
"remove", and "step" commands.
The "installable" (or "A") keyword is a shorthand for all of the
subsystems that are currently available for installation. This is the
default keyword for "list" and "step".
@ installed I
installed I
"installed" is a keyword argument for the "keep", "list", "remove", and
"step" commands. For example, "remove I" requests that all subsystems
that are currently installed and have counterparts in the software
distribution be selected for removal.
An "I" in the third column of a subsystem listing indicates that the
version of this subsystem in the software distribution is already
installed.
The "installed" (or "I") keyword is a shorthand for all of the subsystems
that are installed on the target.
*** Change from old inst ***
The "installed" (or "I") keyword will appear only on subsystem which only
appear on the target.
@ downgrade D
downgrade D
"downgrade" is a keyword argument for the "install", "keep", "list", and
"step" commands. For example, "keep D" requests that all subsystems that
are currently installed and have downgrade counterparts in the software
distribution be left as-is on the disk.
An "D" (downgrade) single letter code in the third column of "list" or
"step" output indicates that a newer version of this subsystem (or a
related subsystem) is installed than is available in the software
distribution. In order to install the downgrade version in the software
distribution, you must give the command "set neweroverride on".
*** Change from old inst ***
The old inst used the letter "N" (or "newer") for downgrade subsystems.
@ upgrade U
upgrade U
"upgrade" is a keyword argument for the "install", "keep", "list", and
"step" commands. For example, "install U" requests that all subsystems
that are currently installed and have newer counterparts in the software
distribution be installed.
An "U" (upgrade) single letter code in the third column of "list" or
"step" output indicates that a version of this subsystem (or a related
one) is installed on the disk. The installed version is older than the
version in the software distribution.
*** Change from old inst ***
The old inst used the letter "X" (or "older") for upgrade subsystems.
@ upgraded u
upgraded u
"upgraded" is a keyword argument for the "install", "keep", "list", and
"step" commands. For example, "list u" shows all subsystems that are
currently on the target that are being removed as part of an installation
of a related (typically newer) version of the product from the
distribution.
An "u" (upgraded) single letter code in the third column of "list" or
"step" output indicates that a this is a subsystem currently installed on
the target, that is about to be removed because a related product on the
distribution is marked for installation.
@ patches
patches
"patches" is a keyword argument for the "install", "keep", "list", and
"step" commands. For example, "install patches" requests all patches that
that are in the software distribution be installed.
@ patchupgrade P
patchupgrade P
"patchupgrade" is a keyword argument for the "install", "keep", "list",
and "step" commands. For example, "install P" requests all patches that
that are in the software distribution and that are upgrades to other
installed patches be installed.
A "P" (patchupgrade) single letter code in the third column of "list" or
"step" output indicates that an older version of this patch is installed
on the target.
@ same S s
same S s
"same" is a keyword argument for the "install", "keep", "list", and "step"
commands. For example, "keep S" requests that all subsystems that are
currently installed and have the same version counterparts in the software
distribution be left as-is on the disk.
An "S" (same) single letter code in the third column of "list" or "step"
output indicates that a same version of this subsystem (or a related
subsystem) is installed.
*** Change from old inst ***
The old inst used the letter "I" (or "installed") for same subsystems.
@ new N n
new N n
"new" (or "N" or "n") is a keyword argument to the "install", "list",
"step", and "keep" commands. This keyword is a shorthand for all of the
subsystems that do not have a version installed., or even a version once
installed and later removed. For example, "install N" requests that all
subsystems that are currently not now and never have been installed on the
target be installed.
An "N" (new) single letter code in the third column of "list" or "step"
output indicates that this subsystem is not installed.
*** Change from old inst ***
The old inst used the space character " " for uninstalled subsystems.
@ notinstalled
notinstalled
"notinstalled" is a keyword argument to the "install", "list", "step", and
"keep" commands. This keyword is a shorthand for all of the subsystems
that do not have a version currently installed. For example,
"install notinstalled" requests that all subsystems that are not installed
on the target be installed.
@ removable L
removable L
"removable" is a keyword argument for the "keep", "list", "remove", and
"step" commands.
The "removable" (or "L") keyword is a shorthand for all of the subsystems
that are currently installed and can be removed from the system. There
are three types of subsystems that might be installed on the system, but
are not removable: maintenance subsystems (i.e. maint*.*.*), subsystems
required for proper operation of IRIS (i.e. eoe1.sw.unix), and subsystems
that must be installed from the miniroot. This third case, subsystems
that must be installed from the miniroot, applies only when inst is
invoked from IRIX rather than the miniroot.
@ uninstalled
uninstalled
"uninstalled" is a keyword argument for the "install", "keep", "list",
"remove", and "step" commands.
The "uninstalled" keyword is a shorthand for subsystems that meet all of
these conditions: they were available for installation in the past, they
are not presently installed, they don't have a version available in the
distribution, and they are not maint* subsystems.
@ ?
?
"?" is a pseudo-command. Use it to redisplay the current menu. Pressing
just the <Enter> key also redisplays the current menu.
@ inst
inst
"inst" is the name of the installation program you are using. It is fully
documented in the inst(1M) manual page and the IRIS Software Installation
Guide. The "help" topic "overview" describes the inst installation
process.
@ more
more
"more?" is a prompt that appears when the output of such commands as
"list", "files", "help" or "set" is longer than one screenful. The output
stops after each screenful and the prompt
more? (h=help)
appears. At this point, you press a key that depends on what you want to
do:
Desired Action: Press:
display next screenful y or space bar
display next line <Enter>
quit this command (no more output) n or q
@ beginner
beginner
See "help overview".
@ overview
overview
inst is the Silicon Graphics software installation tool. If you're a
first-time or infrequent user, please take a few minutes to read this and
learn a few key points about how inst works.
With inst, you install collections of files called subsystems rather than
individual files. Subsystem names have three parts separated by periods,
for example "eoe1.sw.unix". The first part is the product name, the
second part is the image name and the third part is the subsystem.
A typical user's session with inst will help you get an idea of how to use
inst:
1. When inst first comes up, the user checks the first line, "Default
location of of software is <location>", to make sure <location> is the
software distribution source she wants. If not, she uses the "from"
command to specify a different software distribution source.
2. Next, the user gives the "list" command to list the software
(subsystems) that is available for installation. The subsystems that
inst has selected for installation are marked with `i' in the first
column.
3. If the user disagrees with inst about what should be installed and/or
wants to remove software that is no longer needed, she uses the
"install", "remove", "keep" and/or "step" commands until she is
satisfied with the installation and removal selections that the "list"
command displays.
4. The user gives the "go" command to initiate the actual installation
and removal of subsystems.
5. The user gives the "quit" command to leave inst.
The remainder of this "help" topic explains these steps in more detail.
When you first bring up inst, it makes guesses about the location of the
software you want to install and what software you want to install. The
message "Default location of software is ..." tells you this location.
(Hint: you can see this location at any time by giving the "set" command
and looking at the value of "dist".)
If the location that inst has chosen is not correct, the "from" command
allows you to change it. Read "help from" to find out how to use the from
command. (Hint: if you want to install just one product and you are
installing from CD-ROM or a distribution directory on a remote machine, it
is easiest to use a "from" command of the form
"from server:/distdir/product".)
To see what software inst has guessed that you want to install, give the
command "list". If the product descriptions (information about each of
the products in the software distribution) have not been read by inst,
they are read now. A disk space calculation is done next. (Reading
product descriptions and doing disk space calculations takes a few minutes
so they are done only when required. They are not done every time you
give the "list" command.) Finally, the list of subsystems appears.
Some of the subsystems have an i in the first column which means that they
are selected for installation. (Hint: if you would rather start with a
blank slate (i.e. no subsystems selected for installation), give the
command "keep *".) Later, you should read "help list" to get more details
about the list display. You can also ask for "help" on any of the single
characters you see surrounding the subsystem names in the third column.
If you would like to modify the selections that inst has made, there are
several ways to do this. One way to change the selections is the use the
"install", "remove", and "keep" commands. A different way to make your
selections is to use the interactive "step" command. These commands are
cumulative, so you can give them as many times as you need to to make all
of your selections. No software is installed or removed until you give
the "go" command.
Here are some examples of the "install", "remove", "keep" and "step"
commands:
install eoe2.sw.imagetools Select eoe2.sw.imagetools for installation
(mark subsystems with `i' in "list"/"step" output)
remove eoe*.man Select eoe1 and eoe2 manual page subsystems for removal
(mark subsystems with `r' in "list"/"step" output)
install U Update currently installed subsystems (adds `i' to all
subsystems already marked `U' in "list"/"step" output)
step eoe2 Use interactive mode for the subsystems in eoe2: each
subsystem is displayed one at a time and you type one
key to select installation, removal, keep, or retain
current status. See "help step".
keep * Cancel all installation and removal requests (mark
subsystems with `k' or ` ' in "list"/"step" output)
The way to understand the "keep" command is to think "keep things the way
they are". It basically means "don't install a new version" or "don't
remove the current version" or "don't do anything at all" depending on the
circumstances. `*' can be used as a wildcard in names, just as it is used
as a wildcard for file names when you're in the IRIX shell (see
"help wildcard"). Certain special characters and words, such as `U' in
the example above are called `keywords' and stand for groups of subsystems
that share a particular characteristic. See "help keywords" to find out
about keywords.
To see what your current selections are at any time, give the "list"
command without arguments. See "help selection" for more information
about making selections. When you are satisfied with the selections that
"list" shows, give the "go" command to tell inst to perform the
installation and removal of the subsystems you have selected. All of the
pending installation and removal requests (selections) are performed.
inst automatically removes older revisions of the new software you
install, so you do not need to explicitly remove old software first.
When you are done installing and removing software, use the "quit" command
to exit the installation program. If you have installed software from the
miniroot, you are asked if you want to restart the system and you should
answer "yes".
Additional help is available on many topics. The command "help" without
any arguments lists the topics. The IRIS Software Installation Guide is
the reference manual for inst and contains troubleshooting information
which can be useful if you encounter errors. Information about the
specific products you are installing, any compatibility issues with those
products and prerequisites for those products is available from the
Release Notes for the different products.
@ miniroot b
miniroot b
This "help" topic describes the miniroot, a special installation
environment.
The installation program inst can be run as an IRIX command from the
shell, or it can be run from the miniroot. The miniroot is a small set of
programs (the IRIX kernel, a few commands, and inst) that is copied into
the swap partition of a disk after you shut down your workstation and give
some special commands to the PROM Monitor. These commands copy the
miniroot from tape, CD-ROM, or a remote distribution directory to your
swap partition, then boot the miniroot kernel and start the execution of
inst. This procedure is called loading the miniroot and is described
fully in the IRIS Software Installation Guide.
Booting the miniroot kernel, rather than the kernel in /unix, gives inst
the ability to install new versions of all files without the
inconsistencies that could result from replacing programs while they are
running.
Some subsystems must be installed from the miniroot rather than from IRIX.
Situations where proper installation requires reconfiguring the kernel or
where having files temporarily removed would cause system failure are
examples of situations that require miniroot installation.
Some commands on the Administrative Functions Menu can only be performed
while in the miniroot. These are "mkfs", "mount" with arguments and
"umount".
If a subsystem is marked "miniroot", it contains files that must be
installed using the miniroot inst. Miniroot subsystems have a "b"
following their name in "list" and "step" output.
@ required q
required q
"required" is a characteristic of some subsystems and a keyword argument
for the "install", "keep", "list", "remove", and "step" commands.
If a subsystem is "required", it contains programs and files that are
required for proper operation of the workstation. The IRIX kernel is
included in a "required" subsystem for instance. Required subsystems have
a `r' following their name in "list" and "step" output.
The keyword "required" (or just "q") can be used with the "install",
"remove", "keep", "list" and "step" commands as a shorthand for the list
of subsystems that is required.
@ prerequisite
prerequisite
This "help" topic discusses missing prerequisites errors.
Some subsystems require other subsystems also be installed in order to
work correctly. These requirements are known by inst, and it does not let
you install a subsystem that has this type of requirement unless the
subsystem it depends on is already installed or is also selected for
installation. To correct this error condition, install the prerequisite
subsystem, or deselect the subsystem that has the dependency. This error
can be overridden using the "rulesoverride" option. Use this option with
extreme care since not installing prerequisite software can lead to
erroneous system behavior. See "help conflicts" for more on resolving
prerequisite conflicts.
@ nfs
nfs
inst will allow installation of software into directories that have been
NFS-mounted, as long as you have permission to write into those
directories from the local machine.
Since software installations normally take place on the local host, inst
asks the user to confirm installations into NFS-mounted directories.
By setting the "confirm_nfs_installs" resource to false, inst will quietly
install into NFS-mounted directories as long as the user has the
appropriate write-permissions.
@ readerror
readerror
This "help" topic provides information about the possible causes when the
inst program can't read a software distribution.
Read errors can occur in a variety of instances. inst is unable to
distinguish between the different problems, but in some cases error
messages from programs called by inst appear before inst's read error
message and help you determine the source of the problem. Possible
problems are:
o The copy of the software distribution is bad.
o Your version of inst cannot read the software distribution because
they are incompatible. The solution is to install a newer version of
system software (eoe1.sw.unix specifically).
o If you are installing from a tape drive, inst may be having trouble
positioning or reading the tape, or it may not be accessing the
correct tape drive.
o There are I/O problems with the local or remote disk or CD-ROM drive
you are installing software from.
o There are network problems such as a timeout error or a tftp error.
See "help networkerror".
o The account you are using on the remote workstation is protected by a
password.
o The remote workstation went down.
o You have given the wrong pathname for a distribution directory or it
does not contain a complete set of software distribution files.
More information on diagnosing read error problems is available in the
IRIS Software Installation Guide.
@ timeouterror
timeouterror
This "help" topic provides information on network timeout errors.
Network timeout errors occur when inst has established a connection with a
remote workstation, but during one of its read operations, it was unable
to get any blocks for a period of time.
When you get this error, use the "stop" command on the Interrupt/Error
Menu to get back to the Inst Main Menu. Next, use the command "set" and
look at the value of "timeout" to find out the current period of time that
inst is waiting for network input. You can change that period with the
command "set timeout <n>" where <n> is the new timeout period in seconds
(typically in the range of 60 to 300). After changing the network timeout
period, you can proceed with installation, probably by giving the "go"
command.
@ lverror
lverror
This "help" topic provides information on logical volume errors.
If you have an /etc/lvtab file, inst invokes lvinit to initialize the
drivers corresponding to the logical volumes specified in /etc/lvtab. If
lvinit fails, you get an error message from lvinit, while filesystems are
being mounted, before inst is invoked.
You can continue installation without doing anything, but the logical
volume given in the lvinit error message is not accessible. If you want
to fix the problem before continuing with installation, you can escape to
a shell with the "sh" command and repair the problem while in the shell.
The lvinit error message describes the problem and the lvck(1M) manual
page lists the possible causes of logical volume problems.
@ kernelerror
kernelerror
This "help" topic provides information about problems encountered while
configuring the UNIX kernel.
After you give the "quit" command, inst performs several operations to
complete the software installation process. One of these operations uses
autoconfig(1M) to configure a UNIX kernel (i.e. create the file /unix from
several files contained in the software distribution) and put it into a
file called unix (it is /root/unix while you are in the miniroot).
If you get an ERROR IN KERNEL CONFIGURATION message, inst has detected a
problem during autoconfig's kernel configuration process. Possible causes
and their solutions are:
o Tools required by autoconfig or key kernel components are missing.
The tools required by autoconfig and key kernel components are in the
subsystem called eoe1.sw.unix. Re-install this subsystem if there is
a possibility that it is not installed properly or that some files in
it have been deleted since its installation.
o The kernel components present on your system are incompatible.
Kernel components from different releases may not be compatible. To
check for incompatible components, give the "sh" command to escape to
a shell and then give the command "ls -lt /root/var/sysgen/boot/*.o".
By examining the dates, you may be able to identify old .o files that
were part of a release that is incompatible with the new software you
just installed. Use "rm" to remove these old .o files. Return to
inst by giving the "exit" command.
You can run the autoconfig program manually at any time to see what error
messages it gives you or to verify that you have corrected the problem
that caused it to fail. To run autoconfig, give the "sh" command to
escape to a shell and then give the command
chroot /root /etc/autoconfig
If this autoconfig is successful, move the new unix in place by doing:
mv /root/unix.install /root/unix
Once you have corrected the problem that caused autoconfig to fail, you
should be able to give the "quit" command and terminate normally.
@ return
return
"return" is a command on the View and Administrative Commands Menus. It
changes your current menu to the Inst Main Menu.
If you want to execute a command from the Inst Main Menu while you are in
the Administrative Commands Menu, you can give the command
"return <command>". It executes <command> as if your current menu were
the Inst Main Menu, but leaves you in the Administrative Commands Menu.
@ check
check
This "help" topic explains the pre-installation checks that are performed
after you give the "go" command, but before actual installations and
removals are performed. inst checks to see that:
1. All "required" subsystems will be installed after your requests are
completed. Use "help required" for more information.
2. You are using miniroot installation if you have requested that any
subsystems that require miniroot installation be installed. Use
"help miniroot" for more information.
3. The versions of the subsystems you have requested to be installed are
newer that the versions that are presently installed, if any. This
check is not performed if you have given the command
"set neweroverride on".
4. All prerequisites will be satisfied after installation and/or removal
is complete. Use "help prerequisite" for more information.
5. There is enough disk space to install all of your requests. Use
"help spaceerror" for more information.
6. All of the subsystems you have selected for installation are
compatible with each other and the subsystems you already have
installed. Use "help incompatible" for more information.
@ base
base
This "help" topic gives the definition of the phrase "base release".
A base release is a software release that contains all of the files for a
particular software product at a certain release level. These files are
grouped into subsystems with names of the form
<product>.<image>.<subsystem>. You see these names when you give the
"list" and "step" commands. All of the subsystems that have the same
<product> name comprise the base release of a product. (There is an
exception to this: <product> names that begin with "maint" are not
considered base releases.)
@ view
view
"view" is a command on the Inst Main Menu and a short name for the View
Commands Menu.
Give the "view" command when you want to switch to the View Commands Menu.
Alternatively, if you want to execute a command from the View Commands
Menu while you are in the Inst Main Menu, you can give the command
"view <command>". It executes <command> as if your current menu were the
View Commands Menu, but leaves you in the Inst Main Menu.
The View Commands Menu provides a variety of functions to control which
software products are visible when using the "list" and "step" commands.
See "help <command>" for each of the commands on the View Commands Menu to
learn more about them.
The following commands are available from the View Commands Menu, but are
not listed: "quit" and "help".
@ dist
dist
"dist" is a command on the View Commands Menu.
The "dist" command causes the "list" and "step" commands to show software
product versions on the distribution, hiding product versions that are (or
were) installed on the target.
See "help distribution" and "help target" for a discussion of what a
distribution and target are.
@ targ
targ
"targ" is a command on the View Commands Menu.
The "targ" command causes the "list" and "step" commands to show software
product versions that are (or were) installed on the target, hiding
product versions on the distribution.
Invoking the "targ" command turns off the affects of the "dist" command,
and vice versa.
*** Change from old inst ***
In earlier versions of inst, the Main Menu Command "versions" was used to
administer products installed on the target. This "versions" command is
no longer available from within inst.
Instead, use the "view targ" command to switch to target view, and then
use the "list" and "step" commands to manage installed software products.
The "install", "remove" and "keep" commands can be used on any product in
either view ("targ" or "dist").
@ level
level
"level" is a command on the View Commands Menu.
The "level" command with no arguments displays the current view level: (1)
product, (2) image or (3) subsystem.
To change the view level, use the "level" command with one argument,
either a number 1, 2 or 3 or the corresponding word product, image or
subsystem.
When at view level 1, only top level products, such as "eoe1", are
displayed by "list" and "step" commands.
What at view level 2, only second level images, such as "eoe1.sw", are
displayed by "list" and "step" commands.
When at view level 3 (the default), only third level subsystems, such as
"eoe1.sw.unix", are displayed by "list" and "step" commands.
@ sort
sort
"sort" is a command on the View Commands Menu.
The "sort" command controls the order of lines output by the "list" and
"step" commands.
After issuing "sort name" (the default), lines are sorted in alphabetical
order on the product name.
After issuing "sort size", lines are sorted in increasing numeric order on
the products absolute size. Since the default size value displayed (the
default value of the preference show_absolute_sizes) is to show net change
sizes, not absolute, this sort order will appear unsorted unless you set
the preference show_absolute_sizes to the value true.
@ show
show
"show" is a command on the View Commands Menu.
The "show" command displays the current values of the settings available
on the View Commands Menu.
@ maintenance
maintenance
This "help" topic gives the definition of the phrase "maintenance
release".
There are two types of software releases, "base" and "maintenance".
Maintenance releases contain just a few files from one or more software
products. (Base releases contain all files of a single software product,
see "help base".) Files are typically included in the maintenance release
because they contain bug fixes or support for hardware that was released
after the last base release of the software.
The subsystems of maintenance releases are always named
maint<xxx>.<yyy>.<subsystem>. <xxx> is usually a digit or a <product>
name and <yyy> is created from the <product> and <image> names of base
release.
@ distribution
distribution
A collection of installable software in a given location. Also, the media
containing the installable software, such as a compact disk or a
designated disk directory.
If the distribution is set to "none", inst will not load one
automatically. This can save time if you are just removing or browsing
installed software.
@ target
target
The workstation or server that is designated to receive software during an
installation.
@ help
help
"help" is a command on the Inst Main Menu. It is also available from the
Administrative Commands Menu.
Help on software installation is available from the IRIS Software
Installation Guide, from the Release Notes for the software products you
want to install, and from the inst program's extensive online help. To
get online help, use the command
help <topic>
where <topic> is a word of your choice. Almost any word you see on a
menu, single letters you see in the output of "list" and "step", and many
inst "jargon" words have help. If you are unfamiliar with the inst
program or totally confused, start with "help overview". If "help" output
is more than one screen full, a "more? (h=help)" prompt appears after one
screen full. Press the <Space Bar> key to see the next screenful.
The complete list of "help" <topic>s is:
* dist mkfs s
.N distribution more same
.O downgrade mount save
? files n selection
A filter names set
D from networkerror sethostipaddr
I fsname new sethostname
L go nfs sh
N hardware notinstalled show
P help options shroot
R i overview sort
S image patches source
U incompatible patchupgrade space
a inst preferences spaceerror
admin install prerequisite step
all installable product subsystem
args installed q targ
b k quit target
base keep r timeouterror
beginner kernelerror readerror u
check keywords recalculate umount
config level removable uninstalled
conflicts list remove unmount
d load removed upgrade
date lverror request upgraded
default main required view
devices maintenance return wildcard
dir miniroot